Migrate Tasks to Node 16 #81
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reviewers and contributors, please follow the migration to node16 guide we have for in-the-box ADO tasks:
https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode16.md
This PR is not ready to be merged, it is just a starting point to help contributors start.
The Node 16 migration guide is created keeping in mind that the in-the-box ADO tasks were already migrated to Node 10. In order to ensure smooth migration to Node 16, we need to ensure that the task can be run using a Node 10 handler as well. Please refer to the following guide for the same:
https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode10.md
Please be sure to retest all tasks on node 10 and16 thoroughly